2015-02-13 - 17253.100 - Enhancement - Inbound Deliveries in Service Level #SalesDistribution

ENHANCEMENT

17253.100 - Inbound Deliveries in Service Level

Requirement Summary


Need to Integrate inbound deliveries into our existing service level data structure.

Admin Info


Purpose
Need to Integrate inbound deliveries into our existing service level data structure.
Requested By
Kevin Boleware
Spec Created By
Uday Kumar P
Spec Created Date
02/12/2015
Spec QA by
Uday Kumar P
Objects
Service Level
Document Status
Complete

Estimates


SNo
Activity
Estimation in Hours
1
Research
40
2
Documentation
08
3
Development/ Config
50
4
Unit test in DEV
10
5
Unit test in QUA
20
6
Test data & Transports
12

TOTAL
140

References


Prior Tickets

None

Documents

None

Spec Changes



SNo
Change Details
Requested By
Requested On
Notes if any

























Functional Requirement


Purpose/WHY:

In the current dataflow of service level DSO, Third party orders are excluded from the Service level DSO. As per the new requirement from NEC, need to extract the third party orders into service level DSO & Cube. Since the standard extractor is not handling some of fields for third party orders, We need to extract the missing fields into the service level dataflow.

In Scope:

Extracting the TAS orders into a separate DSO, so that the existing DSO is not disturbed.

Out of Scope:

Sales Orders other than TAS Orders.

Solution Summary


1. Need to enhance the existing ZLIKP_LIPS extractor used by Inbound DSO, to fetch Goods movement status(VBUK-WBSTK).
2. Need to enhance the existing ZEKKO_EKKN extractor to fetch Confirmed Quantity(VBEP - BMENG), Requested delivery Quantity(VBEP - WMENG), Confrimed Date(VBEP-EDATU), Requsted delivery date(VBEP-EDATU).
3. Need to create a new staging level DSO ZSD_OTAS for Third party orders. This will be populated with only ‘TAS’ orders from staging level DSO(ZSD_OSSL) & it will also lookup inbound DSO(ZSD_INBD)for all fields mentioned in point 1 & 2. Further mapped to Orders Service level DSO(ZSSL_TAS). Separate DSO is used to ensure that existing dataflow is not disturbed & to make troubleshooting easy.
4. Need to map the Orders Service level DSO ZSSL_TAS with service level cube ZSDC_SSL.
5. Need to add Sales Order number in the Service level Cube & map it with existing service level DSO(ZDSOSSL) & proposed TAS DSO.
6. Need to collect all the corresponding changes into the transport requests.
7. Need to test the source in BPQ(BW 7.3 Quality).

Test Plan


SNo
Test Scenario
Expected Results
1
Need to check if the Third party orders are extracted as per the defined logic & mappings.
All the data should be extracted as per the defined logic & mappings.
2
Need to check if all the dataflow dependencies are collected into the transport request.
All the dataflow dependencies should be collected into the tranport request.

Solution Details


1. Need to enhance the existing ZLIKP_LIPS extractor used by Inbound DSO, to fetch Goods movement status(VBUK-WBSTK).
2. Need to enhance the existing ZEKKO_EKKN extractor to fetch Confirmed Quantity(VBEP - BMENG) and Requested delivery Quantity(VBEP - WMENG),
Confrimed Date(VBEP-EDATU), Requsted delivery date(VBEP-EDATU).
3. Need to create a new TAS DSO for Third party orders. This will be populated with only ‘TAS’ orders from staging level DSO(ZSD_OSSL) & it will also lookup inbound DSO(ZSD_INBD)for all fields mentioned in point
fields mentioned in point 1 & 2. Further mapped to Orders Service level DSO(ZSSL_TAS). Separate DSO is used to ensure that existing dataflow is not disturbed & to make troubleshooting easy.
4. Need to map the Orders Service level DSO ZSSL_TAS with service level cube ZSDC_SSL.
5. Need to add Sales Order number in the Service level Cube & map it with existing service level DSO(ZDSOSSL) & proposed TAS DSO.
6. Need to collect all the corresponding changes into the transport requests.
7. Need to test the source in BPQ(BW 7.3 Quality).

Issues


None